-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(archives): correct recording metadata in S3 tags #105
Conversation
22e8ce6
to
9bce772
Compare
/build_test |
CI build and push: All tests pass ✅ |
1 similar comment
CI build and push: All tests pass ✅ |
6fda4f5
to
9481e18
Compare
9481e18
to
92b085a
Compare
/build_test |
Workflow started at 11/21/2023, 1:03:34 PM. View Actions Run. |
CI build and push: All tests pass ✅ |
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
CI build and push: All tests pass ✅ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Cleans up some archived recording metadata handling and ensures that the
jvmId
andconnectUrl
labels get applied.Related to #62
To test:
./mvnw clean verify
./smoketest.bash -OXtb
, wait for everything to come upPodman > service:jmx:rmi:///jndi/rmi://sample-app:9093/jmxrmi
Before:
(notice that the
connectUrl
label is actually thejvmId
, and there is nojvmId
label)After: